@linuxiac This is perfectly normal for Tumbleweed, it happens any time any major foundational package updates, and is accepted. Yes, the xz mitigation was the cause of it this time, but this isn't that uncommon. glibc updates, for instance, are a very common reason for large update snapshots of Tumbleweed.
For those of you that wonder "How can I contribute?" This short video goes over a fairly simple package version bump in #openSUSE#openbuildservice.
If you've ever asked yourself "Hey new $version of my favourite software is out, when is Tumbleweed going to ship it?" This is how you can help make the process even faster.
I will now try to install #OpenSUSE#MicroOs#Aeon on an old ass laptop I found laying around. #Tumbleweed with #IceWM ran on it, but was really laggy, so let's see if this works better. I doubt it, due to #Gnome being heavier than IceWM, but we'll see!
Huh, being used to Tumbleweed I'm a bit surprised to see #MicroOs#Aeon using X11 instead of Wayland and has the firewall disabled by default. Also I think I've read it uses sysdemd boot but it's installing Grub. Ah well... I don't know anything so what do I know. I'm learning though!
@macberg That shouldn't be happening, unless perhaps you're using the Nvidia proprietary Drivers, I seem to recall that GDM does some weirdness, unless you do some tweaking, making the Wayland session not available.
A shiny new blog post, hopefully helping clarify exactly what the relationship is between #openSUSE#Aeon#microOS and #Kalpa and give a bit of an update of where things are at.
Well, When #Tumbleweed gets it. The packages have all been submitted, and are currently going through #openQA testing and the review process for #openSUSE Factory.
So I can't tell you that. We are downstream of Tumbleweed, and Kalpa will roll Plasma6 sometime after it's accepted into Factory.